Node similarity for component substitution

ABSTRACT

Systems and methods of determining node similarity for component substitution. An example of a method may be carried out by program code stored on non-transient computer-readable medium and executed by a processor. The method includes estimating a normalized similarity metric between the plurality of nodes in the system tree and nodes in other trees. The method also includes assigning a similarity score to each compared node using at least one of: domain based rules, attribute based similarity metrics, and machine learning. The method also includes combining results for cluster analysis.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is related to U.S. patent applications identified by the following U.S. application Ser. Nos. 13/007,229, 13/007,252, 13/007,073, 13/007,175, 13/007,152, 13/007,125, and 13/282,388, each filed the same day as this patent application, and each incorporated by reference for the disclosed subject matter as though fully set forth herein.

BACKGROUND

Manufacturers in various industries use proprietary databases to track the price of individual components used during manufacturing, to determine how the change in price of various components impacts the overall price for their products. For example, a packaging manufacturer may maintain a database including price to obtain the stock materials (e.g., cardboard, plastic, and ink), produce the packaging (e.g., including cutting the cardboard, extruding the plastic, and printing the labels), and delivering the packaging to their customers. When the price of a component changes (e.g., fuel prices rise, thereby raising the price to obtain the stock materials and delivery), the manufacturer is able to use their database to quickly determine the overall impact the component change in price has on the overall price of their product so that the manufacturer can raise the price of their product (or make other adjustments) in a timely manner to reduce or eliminate any impact on their profit.

Manufacturers can also consider the impact of their products on the environment and other parameters. Electronics devices (e.g., computers, printers, and mobile phones), can be a concern because these devices typically have very short lifetimes and are commonly discarded by consumers when newer devices become available. For example, users may discard their mobile phone every two years when they are offered free or discounted equipment to renew their mobile phone contract with their carrier. Consumers also may discard their computers, televisions, and other appliances after only a few years of service, often because it is less expensive to replace than to repair.

Life Cycle Analysis (LCA) databases are beginning to become publicly available. For example, the Open LCA initiative is a public domain data sharing protocol. These databases may include, for example, data related to the mining efforts of raw materials, in addition to the disposal/recycling efforts to handle the components of products after consumers discard the products. These databases have thus far experienced limited adoption.

The databases include vast amounts of data that can be useful to manufacturers given the component breakdown of current products. It is said, for example, that a product as simple as a pen can include over 1500 parameters when considered on a cradle-to-grave basis.

These databases provide no analysis of the data for the manufacturer. For example, while a user may be able to use these databases to check whether the use of a particular plastic might have a bigger impact than another type of plastic, the database still provides no other information that the manufacturer can use to make, e.g., business decisions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a high-level block-diagram of an example computer system that may implement node similarity for component substitution.

FIG. 1B shows an example architecture of machine readable instructions for database program code which may execute program code for determining node similarity for component substitution.

FIG. 2A illustrates an example structure for a multidimensional data structure.

FIG. 2B illustrates a plurality of tree structures that may be provided in the data structure.

FIG. 2C shows an example of a new system tree.

FIGS. 3A-B show an example of determining node similarity for component substitution.

FIG. 4 is a flowchart illustrating example operations of determining node similarity for component substitution.

FIG. 5 is a flowchart illustrating example operations of component substitution that may be implemented.

DETAILED DESCRIPTION

A user may use conventional databases to determine whether a component in a product might have a higher price or a bigger impact than another component. But manufacturing decisions can be more complex than this. Manufacturers may take into consideration a wide variety of characteristics of many different components. Other factors that may also be considered include the intended use of the product, availability of components, customer demand, regulations and laws, to name only a few examples.

As used herein, the term “includes” means includes but not limited to, the term “including” means including but not limited to. The term “based on” means based at least in part on.

In manufacturing, for example, simply substituting a plastic component for a metal component in a product because it has a lower environmental impact may not be possible based on one or more other consideration. For example, a certain type of plastic may indeed have a lower environmental impact, but lacks durability (affecting customer satisfaction and/or warranty). Therefore, the plastic may not be a suitable substitution for the metal component. In another example, the plastic may be more expensive than the metal, or fail on some other parameter. Decisions to substitute components cannot be made by simply consulting a database, without some analysis of many different information paths.

Briefly, systems and methods are disclosed herein which enable automated large-scale data analysis for informed decision-making. It is noted that although the systems and methods are described herein with reference to the design and manufacture of an electronic device, the systems and methods can broadly be applied to the design and implementation (manufacture, management, etc.) of any of a wide range of different types of devices, facilities, and/or services (generally referred to herein as the “system under consideration”).

An example of a system includes a computer readable storage to store at least one system tree having a plurality of nodes. The system tree may be stored in a data structure (e.g., a database). Each node in the system tree represents a characteristic of a component. For example, a system tree for a new computer may include a keyboard node, a motherboard node, a hard disk drive node, and a display node. Each node may also include child nodes. For example, the motherboard node may also include child nodes for motherboard components, such as the onboard memory, and processor. The database may include information about price of the product, environmental impact, performance, product warranty, customer satisfaction, among others, for each of the nodes in the tree. The information may be referred to generally as “cost.” That is, the term “cost” may include price, carbon footprint, energy consumption (e.g., kilowatt hours), number of warranty calls and/or price associated with those warranty calls, and any other suitable metric for characterizing different components.

An analysis engine is operatively associated with the computer readable storage to compare nodes of the system tree with nodes in other trees. For example, the analysis engine may compare nodes of the system tree for the new computer with other trees for other computers. The analysis engine may determine that the other trees for a laptop computer, desktop computer, and netbook computer, all have the same motherboard node (i.e., the same root nodes).

Nodes may be compared, and based on node similarity, at least one node may be substituted or replaced in the system tree with at least one of the nodes from the other trees. For example, if the manufacturer is seeking to produce a “green” or “designed for the environment” computer, the processor node in the system tree may be replaced with the processor node from one of the more energy efficient laptop or netbook computers.

Similarity measures for continuous (and ordinal) data are straightforward. Typically the L1 norm (Manhattan distance) or L2 norm (Euclidian distance) are used. However, no such universal measures exists for categorical data. Prior solutions for comparing nodes in databases are manual, wherein a domain expert examines the nodes and determines similarity. The systems and methods disclosed herein may be used to compute similarity between nodes in databases. Techniques which may be implemented include, but are not limited to, a) domain-based rules, b) attribute-based rules, and c) model-based rules.

In an example, two nodes are considered similar if they are interchangeable in a tree. Techniques and methods disclosed herein may be used to quantitatively determine similarity between two such nodes. Further, given a particular node, these techniques and methods may be used, for example, to obtain a list of k most similar nodes from a specific database.

In addition, nodes that are found to be similar may also be rated. A higher rating may indicate a better candidate for substitution. For example, the motherboard node for the netbook computer may receive a higher rating for price than the desktop computer, because the price of the motherboard in the netbook computer is lower than the price of the motherboard in the desktop computer. But the motherboard node of the laptop computer may receive a higher rating than the desktop computer for environmental impact, because the processor in the laptop computer is more energy efficient than the processor in the desktop computer. In addition, the processor in one type of laptop computer may be made of more environmentally friendly components than the processor in another laptop computer.

The systems and methods described herein determine node similarity to enable node comparison. Understanding node similarity aids in finding suitable substitutions, and for clustering nodes or applying other analysis where a distance metric between nodes can be implemented. The node comparison may be utilized for component substitution for device manufacture based on a knowledge base of information for existing components to meet or exceed customer expectations, marketing goals, environmental impact, and/or other considerations, without the need to develop new components.

FIG. 1A is a high-level block-diagram of an example computer system 100 which may implement node similarity for component substitution. System 100 may be implemented with any of a wide variety of computing devices, such as, but not limited to, stand-alone desktop/laptop/netbook computers, workstations, server computers, blade servers, mobile devices, and appliances (e.g., devices dedicated to providing a service), to name only a few examples. Each of the computing devices may include memory, storage, and a degree of data processing capability at least sufficient to manage a communications connection either directly with one another or indirectly (e.g., via a network). At least one of the computing devices is also configured with sufficient processing capability to execute the program code described herein.

In an example, the system 100 may include a host 110 providing a service 105 accessed by a user 101 via a client device 120. For purposes of illustration, the service 105 may be a data processing service executing on a host 110 configured as a server computer with computer-readable storage 112. The client 120 may be any suitable computer or computing device (e.g., a mobile device) capable of accessing the host 110. Host 110 and client 120 are not limited to any particular type of devices. It is also possible for the host 110 and client 120 to be the same device (e.g., a kiosk platform). Although, it is noted that the database operations described herein which may be executed by the host 110 are typically better performed on a separate computer system having more processing capability, such as a server computer or plurality of server computers. The user interface may be provided on any computing device for providing data to, and receiving data from, service 105.

The system 100 may also include a communication network 130, such as a local area network (LAN) and/or wide area network (WAN). In one example, the network 130 includes the Internet or other mobile communications network (e.g., a 3G or 4G mobile device network). Network 130 provides greater accessibility to the service 105 for use in distributed environments, for example, where more than one user may have input and/or receive output from the service 105.

In an example, the host 110 is implemented with (or as part of) the service 105 in the networked computer system 100. For example, the service 105 may be a cloud-based service, wherein the host 110 is at least one server computer in a cloud computing system. The host 110 may be provided on the network 130 via a communication connection, such as via an Internet service provider (ISP). In this regard, the client 120 is able to access host 110 directly via the network 130, or via an agent, such as a network site. In an example, the agent may include a web portal on a third-party venue (e.g., a commercial Internet site), which facilitates a connection for one or more clients 120 with host 110. In another example, portal icons may be provided (e.g., on third-party venues, pre-installed on a computer or mobile device, etc.) to facilitate a communications connection between the host 110 and client 120.

Before continuing, it is noted that the host 110 is not limited in function. The host 110 may also provide other services to other computing or data processing systems or devices in the system 100. For example, host 110 may also provide transaction processing services, email services, etc.

In addition, the host 110 may be operable to communicate with at least one information source 140. The source 140 may be part of the service 105, and/or the source 140 may be distributed in the network 130. The source 140 may include any suitable source(s) for information about various components. For example, the source 140 may include manufacturer specifications, proprietary databases, public databases, and/or a combination of these, to name only a few examples of suitable sources. The source 140 may include automatically generated and/or manual user input. If the source 140 includes user-generated data, an appropriate filter may be applied, e.g., to discard “bad” data or misinformation. There is no limit to the type or amount of information that may be provided by the source 140. In addition, the information may include unprocessed or “raw” data. Or the data may undergo at least some level of processing.

The host 110 may execute analytics using the information from the source 140 to generate output for use in component substitution for device manufacture. For example, the host 110 receives information from the source 140 including environmental impact based on a cradle-to-grave assessment for various components that may be used. The host 110 may maintain the results in at least one data structure (e.g., a matrix or table or database) in computer-readable media 115. The data structure may be accessed by the host 110, which performs analytics based on input by the client 120, and outputs the results for the user at the client 110.

In an example, the host 110 performs the analytics described herein by executing database program code 150. The database program code 150 may include an analysis engine 152 and a query engine 154. In an example, the analytics engine 152 may be integrated into the query engine 154. The analytics engine 152 may be an SQL-based analytics engine, and the query engine 154 may be an SQL query engine. However, the operations described herein are not limited to any specific implementation with any particular type of database.

A system that implements component substitution as described herein has the capability to take a description of a system under consideration (e.g., including in terms of inherent properties of the device or service), and assess the characteristics (e.g., price, environmental footprint, customer satisfaction, warranty) of the individual components. The system may then output a list of substitute components and/or an assessment of various product designs. Component substitution may be better understood with reference to the following discussion of an example implementation of machine readable instructions.

FIG. 1B shows an example architecture of machine readable instructions for the database program code 150 which may execute program code for determining node similarity for component substitution. In an example, the database program code 150 may be implemented in machine-readable instructions (such as but not limited to, software or firmware) stored on a computer readable medium (e.g., storage 115 in FIG. 1A) and executable by one or more processor (e.g., on host 110 in FIG. 1A) to perform the operations described herein. The database program code 150 may perform operations on at least one database 160 (or other data structure). The database 160 may be provided on the same or different computer readable medium (e.g., storage 115 in FIG. 1A). It is noted, however, the components shown in FIGS. 1A and 1B are provided only for purposes of illustration of an example operating environment, and are not intended to limit execution to any particular system.

During operation, the analysis engine 152 may be operatively associated with the query engine 154 to execute the function of the architecture of machine readable instructions as self-contained modules. These modules can be integrated within a self-standing tool, or may be implemented as agents that run on top of an existing database. Existing data are used as seed data to populate a matrix. A comparison is then run between the device and the populated matrix using node comparison techniques (and related algorithms). After a set of similar nodes has been identified, trees are constructed to identify the structure resident within the similar nodes. The constructed tree is then compared to the system tree. When a similar tree (or set of trees) has been identified, the tree(s) are assessed for one or more parameter (e.g., environmental footprint). In an example, one or more node (e.g., portions of trees or even entire trees) may be substituted in the system tree. For example, the offending node(s) may be replaced with potentially better rated nodes, and also assessed to identify a better rated tree. The highly-rated tree(s) are used to mine the populated matrix for novel sub-trees from other devices, which may lead to a better rated solution.

In an example, the architecture of machine readable instructions may include a matrix completion module 170. The matrix completion module 170 may populate the database with information related to various devices. The information may include price and environmental impact, among other characteristics. Existing data from commercial databases, published literature, or internal systems may be used as seed data. The seed data is then expanded through one or more of data mining, knowledge discovery, regression, and/or other techniques. In this manner, a few starting points of readily available data are used initially, and more comprehensive information can be constructed for the database.

The architecture of machine readable instructions may also include a node similarity module 171. The node similarity module 171 may be used to identify relevant characteristics of the device being assessed. These characteristics may be relevant to at least one of the parameters. For example, the published energy use rate for the device is directly related to environmental impact. But the characteristics may also include part name, part number, composition of the device, etc. The relevant characteristics of the device are then compared to the matrix of information in the database to identify any similar nodes. These nodes may be considered to be similar at the root (e.g., two different laptop computers), or similar in terms of other relational characteristics (e.g., a computer housing and a printer housing).

The architecture of machine readable instructions may also include a tree reconstruction module 172. After a group of related nodes have been identified, the tree reconstruction module 172 further outlines how the identified nodes are structurally related to one another. In an example, a root node is detected or inputted, and then the remaining nodes are identified as children or non-children of the root node. Based on the identified children nodes, a hierarchical structure may be generated which is used to construct a tree.

The architecture of machine readable instructions may also include a tree similarity module 173. After constructing a tree of relevant nodes from the populated matrix, this tree is then compared to the system tree. The system tree may be assessed, and a bill-of-materials developed for the device. Examples of methods to identify metrics for comparing two trees, include but are not limited to, tree depth, breadth, and distance between relative nodes. The output may include a similarity rating relative to identified trees of relevance in the populated matrix.

The architecture of machine readable instructions may also include a tree substitution and design module 174. After two or more trees of relevance have been identified, opportunities to replace “offending” nodes in the system tree may be sought. For example, a laptop computer may be identified as being similar to another laptop computer stored in the database. Suppose the processors of each laptop computer are identified as the offender. Then, if the processor of another laptop computer tree has a lower environmental footprint than the processor in the system tree, the processor node in the other laptop tree may be substituted for the processor node in the system tree. The new system tree results in a laptop computer having a lower environmental footprint. Next, the tree substitution and design module moves on to the next highest offender (e.g., the hard disk drive node), and the process repeats. The output results in a new tree for the device having a lower environmental footprint.

The architecture of machine readable instructions may also include a tree assessment module 175. The tree assessment module 175 may be used to assess a device, rather than redesign the device. In an example, the total environmental footprint of the tree may be calculated based on the similarity metrics identified by the tree similarity module. Methods to rapidly calculate the footprint of very large trees based on a hierarchy of nodes with similar grouping may be utilized. The output of the tree assessment module may include an estimated environmental footprint of the system tree. Additional metrics of relevance may also be output. For example, additional metrics may include but are not limited to, the minimum calculated environmental footprint of substitutive trees, the most similar tree with a lower environmental footprint, and the average footprint of all relevant trees.

The architecture of machine readable instructions may also include a tree creation module 176. The tree creation module 176 utilizes output from the other modules (e.g., the tree reconstruction module 172 and the tree substitution module 174) to create new trees. The fundamental principle is that different systems may perform similar functions, but not necessarily be previously viewed in similar fashion. For example, a server computer may use a particular component hierarchy in the supply chain that is also relevant to a laptop computer. But the manufacturer may not have considered such a hierarchy for numerous reasons, not the least of which is the manufacturer's own belief that server computers are different than laptop computers.

It is noted that the functional modules are shown for purposes of illustration. Still other functional modules may also be provided. In addition, the functional modules may be combined with one another.

As noted above, the database 160 may store at least one tree with a plurality of nodes. Each node in the tree represents at least one characteristic of a device. For example, the database 160 may include a tree for a new computer. The new computer tree may include nodes for the motherboard, the hard disk drive, the keyboard, and the display. The motherboard node may include information about cost, e.g., at least one of price, environmental impact, performance, product warranty, and customer satisfaction, among other characteristics of the motherboard.

In an example, the database 160 may be a multidimensional data structure. FIG. 2A illustrates an example structure for a multidimensional data structure. In this example, the database is configured as a matrix 200 with information for each node. Example information may include, but are not limited to the following characteristics: price, environmental impact, performance, product warranty, and customer satisfaction, to name only a few examples.

In FIG. 2A, the matrix 200 includes a plurality of columns (A, B, . . . i) and a plurality of rows (1, 2, . . . j). The intersection of each row and column may be referenced by the combination of row label and column label. For example, the intersection of column B and row 2 may be referred to as B2. In an example, each row corresponds to a component, and is thus used to generate the nodes in trees. The columns correspond to characteristics for the components. In an example where column B is for a computer display and row 2 is for environmental impact, the intersection B2 may include environmental impact information (e.g., overall carbon footprint) for the computer display.

The matrix 200 is not limited to the two-dimensional example given above. In another example, the program code may go to the intersection B2, and then read forward/backward in a third dimension to obtain more detailed environmental impact information included in the overall carbon footprint calculation, such as but not limited to, energy use, toxic emissions, and waste disposal. For purposes of illustration, the addresses in the third dimension may be referenced using any suitable symbols, such as subscripts, wherein the address is B2 ₁, B2 ₂, . . . B2 _(k).

The information in the multidimensional data structure may be included in, or referenced by the nodes in the trees. For example, a printed circuit board node may reference intersection B2 in the matrix 200 for environmental impact information related to that particular printed circuit board. It is noted that multiple nodes in different trees may reference the same address in the same matrix 200. By way of illustration, the printed circuit board nodes in a plurality of different computer trees may each reference the intersection B2 in the same matrix 200, if intersection B2 includes information for environmental impact that is the same for each printed circuit board.

The matrix 200 shown in FIG. 2A is shown and described herein as an example of an example of a data structure that may be used. It is noted, however, that the tree structures may be based on information provided in any suitable format(s).

The tree structure provided in the database may be better understood from the following discussion with reference to FIG. 2B. FIG. 2B illustrates a plurality of tree structures 210 a-e that may be provided in the database. The trees 210 a-e each have a plurality of nodes. Each node in the tree 210 a-e may further include subnodes, thereby defining a child-parent relationship between the nodes, and providing additional layers of granularity for the components.

For purposes of illustration, the tree structures 210 a-c are for computer devices. It is noted that any suitable number and type of other trees may be also used. For example, tree structure 210 d is for a printer, and tree structure 210 e is for a mobile phone. Accordingly, nodes that are suitable for substitution may be found in system trees that are not necessarily related to one another in a conventional sense. For example, a computer is different than a printer in most regards, which is different than a mobile phone. But there may be overlap in at least one of the nodes. For example, computers, printers, and mobile phones all have in common a processor, some degree of memory, and a housing.

In this example, all of the trees 210 a-e (even the printer and mobile phone trees) include motherboard nodes 211 a-e, in addition to nodes for other components. At least some of the other component nodes may be related in the different trees (e.g., nodes 201 a-c are related). At least some of the other component nodes may not be related in the different trees (e.g., node 203 for ink cartridges in the printer tree 210 d and node 204 for the antenna in the mobile phone tree 210 e).

Continuing with this example, motherboard nodes 211 a-c may include subnodes 212 a-c for the circuit boards, subnodes 213 a-c for the onboard memory, and subnodes 214 a-c for the processors. These subnodes are each related to the respective motherboard nodes 211 a-c as child nodes. Furthermore, the child nodes may also have child nodes of their own. For example, the circuit board nodes 212 a-c may include child nodes 215 a-c for the wafer and child nodes 216 a-c for the metal traces.

During operation, program code (e.g., the database program code 150 in FIGS. 1A and 1B) is executed to create a system tree (e.g., system tree 210 a in FIG. 2B) for a new system (e.g., a new laptop computer). The program code is also executed to identify and analyze other trees (e.g., system trees 210 b-e). In an example, the program code traverses the trees and detects at least one root node in each of the trees. For example, the program code may compare nodes of the new system tree 210 a with laptop/netbook computer trees 210 b, desktop computer trees 210 c, printer trees 210 d, and mobile phone trees 210 e. Each of the trees may include root nodes for motherboards (nodes 211 a-e in FIG. 2B). Root nodes may also be identified for one or more subnode. Accordingly, the motherboard node 211 a (and/or the subnodes) in the system tree 210 a for the new system is compared to the motherboard nodes 211 b-e in the other trees 210 b-e.

The program may also be executed to rate the nodes. The nodes may be rated based on information in the database (e.g., in matrix 200 in FIG. 2A), to determine the suitability of a substitution. In an example, a higher rating may indicate a better candidate for substitution than a lower rating (although the opposite may also be true). For example, the motherboard node 211 b of one of the laptop/netbook computer trees 210 b may be assigned a higher rating for price than the motherboard node in the desktop computer trees 210 c, because the price of the motherboard in the netbooks is lower than the price of the motherboard in the desktop computers. The motherboard node of the desktop computer trees 210 c may be assigned a higher rating than the netbooks for performance. But the motherboard node 211 b of the laptop/netbook computer trees 210 b may receive higher ratings than the desktop computer trees 210 c for environmental impact, because the processor in the laptop/netbook computers is more energy efficient.

The processor in one type of laptop computer may be more energy efficient than the processor in another laptop computer, and therefore the motherboard node for one of the laptop computer trees 210 b may receive a higher rating than the motherboard node for the other laptop computers in the same group of trees 210 b. The ratings may also be weighted. For example, environmental impact may receive a higher weighting if environmental impact is more pertinent to the user than price.

After a suitable substitution is determined, the program code may further be executed to create a new tree for the new system using node replacement or substitution based on nodes and/or subnodes in other trees. FIG. 2C shows an example of a new system tree 220. In this example, the new tree 220 is created from the tree 210 a. But the new tree 220 is created with the node 215 b from the laptop computer tree 210 b because this node has the best rating for environmental impact. The new tree 220 is also created with the node 214 c from the desktop computer trees, because this node has the best performance. The new tree 220 is also created with the node 212 e from the mobile phone tree because this node has the lowest price.

It is readily appreciated from the above discussion that the systems and methods may be utilized to provide a quick assessment of a large amount of manufacturing information for a wide variety of different systems, and with high accuracy. The systems and methods may be used to modify the design of many types of systems, such as device manufacture, by reducing the price to manufacture, reducing the impact the device has on the environment, and reducing warranty calls, all while increasing customer satisfaction with the product. These considerations are particularly relevant for so-called “fleet” customers or enterprise customers who purchase in large quantities, and therefore carefully consider the many different impacts of their purchases.

In this regard, the systems and methods may be implemented as a product assessment service. For example, the systems and methods may be used by enterprises who demand emissions reduction or compliance with environmental goals and/or regulations. Many of these enterprises are turning to their vendors to help assess, monitor, and reduce their environmental footprint. The systems and methods not only enable manufacturers to competitively reduce the environmental footprint of their customers, but to also competitively reduce the environmental footprint of their own supply chain.

These considerations are also relevant to consumers who are becoming more conscious of the impact their own purchases have on the environment.

In addition to environmental impact, the systems and methods also provide the foundation for significant savings, both direct (e.g., supply-side) and indirect (e.g., reducing warranty calls). The ability to automate product analysis may be a differentiator for some manufacturers in reducing price for smaller customers, and scaling to meet the demands of larger customers, while maintaining or even growing profit margins.

FIGS. 3A-B show an example of determining node similarity for component substitution. In this example, each entity in the database is referred to as a node 300. Each of a plurality of nodes 300 is associated with a set of attributes. The attributes (illustrated by 310 a-d, 311 a-d, 312 a-d, and 313 a-d for nodes 301-304, respectively) may be numerical, discrete, categorical, textual description, visual, auditory, etc. Examples of some attributes include, but are not limited to: database source, part number, part name, part description, category, subcategory, trees containing that node, images, etc. The object is to estimate a normalized similarity metric between any two nodes belonging to the same or different databases.

More detailed matching techniques are described in detail below. For now it is sufficient to understand that attributes may be analyzed, for example, by comparing at least one measurable aspect. For example, comparing text using the longest common string march for matching text strings, pixel matching for matching pictures, and so forth.

A similarity metric of one indicates a match (e.g., the same node or nodes that are always interchangeable). For example, nodes 301 and 302 for the processor of two different laptop computers are assigned a similarity metric of one because the nodes 301 and 302 are identical (all attributes match). A similarity metric of zero indicates no match (e.g., in no situation can one node substitute for the other). For example, nodes 301 and 303 for the laptop and printer are assigned a similarity metric of zero because the processors are not interchangeable (no attributes match. Intermediate values between 0 and 1 indicate various degrees of similarity between the nodes. For example, nodes 303 and 304 for the printer and a mobile phone are assigned a similarity metric of 0.8 because the processors have sufficient common attributes that the processors may be interchangeable for some uses (some attributes match).

Knowledge of similarity between two nodes also enables a corresponding distance metric to be estimated. For example, if “s” represents similarity, then “1−s” or “1/s” or other similar mappings may be used to represent a distance metric between nodes. Since one can be derived from the other, the discussion herein refers to similarity and distance metrics interchangeably.

For purposes of illustration, three techniques of estimating similarity between nodes are described in detail below. It is noted, however, that the systems and methods are not limited to implementation by any particular technique. Other suitable techniques will also be readily apparent to those having ordinary skill in the art after becoming familiar with the teachings herein. In addition, any of these and/or other techniques may be combined in any of a wide variety of ways, with the possibility of one or more being used simultaneously with the user combining the results together to arrive at a similarity number, e.g., by weighted sum.

In a first example, a domain-based rules technique may be employed. This technique uses domain knowledge about the databases, the nodes within the databases, and any available contextual information, to construct a set of rules. The rules may then be used to determine the similarity between two nodes. For purposes of illustration, a simple rule may be defined such that two nodes from the same or substantially similar data source and having the same or substantially similar part numbers are assigned a similarity of one. Of course other rules could exploit specific knowledge of attributes of nodes.

In a second example, an attribute-based similarity metric may be employed. Multivariate attributes, typically available for each node, are used to compute a similarity metric. The final similarity metric comprises the similarity in each individual attribute. For purposes of illustration, the final similarity metric may include the weighted sum of the similarity of each of the attributes. The similarity function for each attribute may be defined by a domain expert. For example, similarity between string attributes may be computed from the longest common subsequence (LCS) match. In another example, similarity may be based on longest common prefix (LCP). In another example, similarity may be based on a combination of LCS and LCP. In yet another example, similarity may be computed using Levenshtein distance between strings. Other string matching algorithms may also be used. For example, similarity between numeric attributes may be computed using Minkowski distance.

The manner of combining the similarity of attributes may also be based on domain knowledge (e.g., determining the weights, if the weighted sum is used). The similarity of attributes may also be based on the usage scenario of the similarity metric.

In one example, the similarity metric between two nodes may be determined as follows: S(N1·N2)=(1/Z)ΣWi*si(A1i,A2i)

where:

-   -   S( ) is the node similarity function;     -   N1, N2 are the nodes;     -   Wi is the weight assigned to the ith attribute similarity;     -   si( ) is the function that computes the similarity between the         nodes' ith attribute A1 i, A2 i are the ith attributes of the         two nodes, respectively; and     -   Z is a normalization constant.

The similarity metric between two nodes may be determined using cosine similarity to compare two vectors of attributes. The similarity metric may be determined as the dot product between the two attribute vectors, divided by the magnitude of both the vectors, as follows: S=(A1−A2)/(|A1|A2|)

In a third example, a model-based similarity metric may be employed. In this technique, the similarity between two nodes is based on data that is available, such as but not limited to: textual descriptions of each of the nodes, a large number of trees consisting of the nodes, data where similarity between nodes is already known (e.g., has been assigned manually by a domain expert).

In an example, if text descriptions of the nodes are available, topic models may be constructed for each node. These models may then be compared to determine the similarity between the nodes.

In another example, if a large number of trees are available, contextual metrics may be computed for each node. These metrics pertain to the proximity of other nodes to a given node. For example, if the parent and children of two nodes are always the same, those nodes are likely to have a high similarity to one another.

In another example, a “labeled” data set is already available. In other words, the similarity between any two nodes in the data set is known. Such a data set can be used for training a machine learning model. The input to the model includes “features” extracted from the node attributes. The output is the similarity metric. A trained model, which has learned the relationship between the node features and the similarity metric, may be used to determine the similarity between two new nodes for which the similarity is not known, but the same features can be extracted from their attributes.

Note that, the similarity metric does not have to be symmetric. That is, S(N1, N2)≠S(N2, N1), where S( ) denotes the similarity function, and N1, N2 are two nodes. Because S(N1, N2) denotes the substitutability of N1 with N2, N1 with N2 may not always be the same as the substitutability of N2 with N1. Indeed, if all attributes of N1 are subsumed in N2, then N2 may be able to replace N1, but not vice-versa. That is, S(N1, N2)=1, while S(N2, N1)<1 or even 0.

After selecting at least one of the techniques for determining similarity (or distance) metric, the technique(s) may be used to compute the similarity between any two nodes in a database. The similarity may then be used to construct a distance matrix between nodes of the database. The matrix can then be used to perform cluster (or group) analysis. The resulting clusters may be manually labeled by a domain expert. Clustering may also be used to approximate matching of nodes in two difference databases that do not share common attributes. Both databases may be separately clustered, and the clusters manually labeled for use. Thus, the task of matching nodes is reduced to matching the cluster labels of the two databases.

Before continuing, it should be noted that the examples described above are provided for purposes of illustration, and are not intended to be limiting. Other devices and/or device configurations may be utilized to carry out the operations described herein.

FIGS. 4 and 5 are flowcharts illustrating example operations which may be implemented. Operations 400 and 500 may be embodied as machine readable instructions on one or more computer-readable medium. When executed on a processor, the instructions cause a general purpose computing device to be programmed as a special-purpose machine that implements the described operations. In an example implementation, the components and connections depicted in the figures may be used.

FIG. 4 is a flowchart illustrating example operations of determining node similarity for component substitution. In operation 410, a normalized similarity metric is estimated between the plurality of nodes in the system tree and nodes in other trees. In operation 420, a similarity score is assigned to each compared node using at least one of: domain based rules, attribute based similarity metrics, and machine learning. Domain-based rules may use domain knowledge to construct a set of rules based on node attributes. Attribute based similarity metrics may be determined based on multivariate attributes for each node. Model based similarity may be determined based on available node data.

In an example, a similarity score of one indicates interchangeable nodes. A similarity score of zero indicates no match. In operation 430, results are combined for cluster analysis. Accordingly, the similarity score may be used to compute similarity between any two nodes in a database. It is noted that the similarity score is asymmetric.

The operations discussed above are provided to illustrate various examples of determining node similarity for component substitution for device manufacture. It is noted that the operations are not limited to the ordering shown. Still other operations may also be implemented.

For purposes of illustration, further operations may include rating the nodes based on respective similarity scores, and replacing the at least one of the common nodes in the system tree is based on the rating.

FIG. 5 is a flowchart illustrating example operations of component substitution which may be implemented. In operation 510, building a system tree having a plurality of nodes, each node in the system tree representing a characteristic of a component of a system under consideration. For example, a tree may be for a new laptop computer. The tree may include a motherboard node, a keyboard node, a hard disk drive node, and a display node. The keyboard node may further include a housing node, a cabling/wireless node, and a circuit board node. In this example, the keyboard node is the parent node and the housing node, cabling/wireless node, and circuit board node are child nodes of the keyboard node. Any degree of granularity may be utilized based at least to some extent on design considerations (including desired output, and time to process).

In operation 520, comparing nodes of the tree with nodes in other trees to identify common nodes (or root or similar node). Continuing with the example from operation 510, the tree for the new laptop computer may be compared with trees for other computers, such as other laptop computers, netbook computers, desktop computers, servers, server blades, etc. The common node may be the keyboard node in each of these other trees. Or the common node may be the circuit board child node for the keyboard node or even the motherboard node.

It is noted that, in this example, the tree for the new laptop computer may also be compared with trees for other, at least somewhat unrelated systems. For example, the processor or memory in a mobile phone may be a suitable substitute for the processor or memory in another system, such as a printer.

In operation 530, generating a new tree for the system under consideration by replacing at least one of the common nodes in the system tree with at least one of the nodes in the other trees. For example, the processor from another laptop computer may be substituted for the processor originally chosen for the new laptop computer to give the new laptop computer a lower environmental impact, lower price, higher customer satisfaction, longer warranty, etc. than the initial design for the new laptop computer may have delivered.

It is noted that various of the operations described herein may be automated or partially automated. For example, building system trees may be fully automatic using retrieval routines executed by program code. Alternatively, at least some user interaction may be provided. In such an example, the user may manually provide production specification(s), and then building system trees may be automatic based at least in part of the user-provided product specification(s). The level of user interaction may be any suitable degree. For example, the user may simply identify that the new system is to be an inkjet printer. Alternatively, the user may identify individual components of the inkjet printer, including but not limited to, the type of ink cartridges, processor speed, memory size, and paper tray options.

In an example, the component substitution operations may be implemented with a customer interface (e.g., web-based product ordering interface). The customer is able to make predetermined selections (e.g., specifying minimum processor speed), and the operations 510-530 described above are implemented on a back-end device to present the user with various designs that meet the customer's minimum expectations. The user can then further select which of the alternatives best suit the customer's preferences (e.g., for price, environmental impact, customer satisfaction, and warranty).

Further operations may also include rating the nodes, wherein replacing the at least one of the nodes in the system tree is based on the rating of the nodes. For example, a processor having a higher energy efficiency rating may receive a higher ranking for environmental impact. A processor that is priced lower may receive a higher ranking for price. A processor that has a higher customer satisfaction may receive a higher ranking for customer satisfaction. The rankings may further be weighted. For example, if the user values a lower environmental impact above price, then the rating for environmental impact is assigned a higher weight than price.

Still further operations may also include populating a database with characteristics of a plurality of components. The characteristics of the components may include price, environmental impact of the components, customer satisfaction, warranty, and other characteristics dependent at least to some extent on design considerations. Some design considerations may include which characteristics are desired by the user, required by regulation, set forth in company policy, and used to meet manufacturing goals, to name only a few examples.

Still further operations may also include identifying structural relationships between the plurality of nodes in the system tree and the nodes in the other trees. For example, structural relationships may include, but are not limited to, parent-child nodes, and parent-grandchildren nodes.

Still further operations may also include determining at least one substitute component for the system under consideration based on the new tree. In an example, further operations may include outputting a bill of materials with the at least one substitute component based on the new tree. The bill of materials may be printed for a user (e.g., a consumer). In an example, the bill of materials may be vetted (e.g., by a design engineer) to ensure that any substitutions are appropriate. For example, a high-efficiency processor for a laptop computer may not be an appropriate substitution for a mobile phone.

It is noted that the examples shown and described are provided for purposes of illustration and are not intended to be limiting. Still other embodiments are also contemplated. 

The invention claimed is:
 1. A method of determining node similarity for component substitution, the method carried out by program code stored on non-transient computer-readable medium and executed by a processor, the method comprising: determining similarity metric values between nodes of a target system tree associated with a target system and nodes in other system trees respectively associated with other systems, wherein each system comprises components and nodes of each system tree represent respective ones of the components of the associated system, wherein the determining comprises comparing nodes of the target system tree with respective nodes of the other system trees by applying at least one of domain based rules and attribute based similarity metrics to attributes of the system components represented by the nodes being compared, and assigning a similarity score to each node of the other system trees compared to a respective one of the nodes of the target system tree based on results of the comparing; and for at least one of the nodes of the target system, identifying replacement ones of the nodes of the other system trees based on their respective assigned similarity scores.
 2. The method of claim 1, further comprising rating the nodes based on respective similarity scores, and replacing the at least one node of the target system tree with a respective one of the identified replacement nodes based on the rating.
 3. The method of claim 1, wherein domain-based rules uses domain knowledge to construct a set of rules based on node attributes.
 4. The method of claim 1, wherein domain-based rules include heuristics related to at least one of databases, nodes within the databases, and contextual information.
 5. The method of claim 1, wherein attribute based similarity metrics are based on multivariate attributes for each node.
 6. The method of claim 5, wherein the multivariate attributes include at least one of LCS, LCP, Levenshtein distance, Minkowski distance, weights assigned to each attribute, and dot product between two attribute vectors.
 7. The method of claim 1, wherein the assigning comprises using a model based similarity metric that is determined based on available node data in assigning the similarity score to each compared node.
 8. The method of claim 7, wherein the model based similarity metric uses at least one of textual descriptions of each node, data where similarity between nodes is known, topic models, and contextual metrics.
 9. The method of claim 1, wherein the similarity score is used to compute similarity between any two nodes in a database.
 10. A system determining node similarity for component substitution, comprising: a non-transitory computer readable storage to store system trees comprising sets of nodes, wherein a system tree is associated with a respective system, each system comprises components, and nodes of each system tree represent components of the associated system; and an analysis engine operatively associated with the computer readable storage to perform operations comprising determining similarity metric values between nodes of a target one of the system trees and nodes in other ones of the system trees, wherein the determining comprises the analysis engine comparing nodes of the target system tree with nodes of the other system trees by applying at least one of domain based rules and attribute based similarity metrics to attributes of the system components represented by the nodes being compared, and the analysis engine assigning a similarity score to each node of the other system trees compared to a respective one of the nodes of the target system tree based on results of the comparing.
 11. The system of claim 10, wherein the analysis engine rates the nodes based on respective similarity scores, and replacing the at least one of the common nodes in the system tree is based on the rating.
 12. The system of claim 10, wherein a similarity score of one indicates interchangeable nodes, and a similarity score of zero indicates no match.
 13. The system of claim 10, wherein the similarity score is used for cluster analysis.
 14. The system of claim 10, wherein domain-based rules uses domain knowledge to construct a set of rules based on node attributes.
 15. The system of claim 10, wherein attribute based similarity metrics are determined based on multivariate attributes for each node.
 16. The system of claim 10, wherein the analysis engine uses a model based similarity metric that is determined based on available node data in assigning the similarity score to each compared node.
 17. The system of claim 10, wherein the similarity score is used to compute similarity between any two nodes in a database.
 18. A system for determining node similarity for component substitution, comprising: an analysis engine operatively associated with a non-transitory computer readable storage to perform operations comprising determining similarity metric values between nodes of a target system tree associated with a target system and nodes in other system trees respectively associated with other systems, wherein each system comprises components and nodes of each system tree represent respective ones of the components of the associated system, wherein the determining comprises the analysis engine comparing ones of the nodes of the target system tree with respective ones of the nodes of the other system trees by applying at least one of domain based rules and attribute based similarity metrics to attributes of the system components represented by the nodes being compared, and the analysis engine assigning a similarity score to each node of the other system trees compared to a respective one of the nodes of target system tree based on results of the comparing.
 19. The system of claim 18, wherein the similarity score is used for cluster analysis.
 20. The system of claim 18, further comprising the analysis engine rating the nodes of the other system trees based on their similarity scores, and the analysis engine replacing the at least one of the common nodes in the system tree based on the rating. 